[VoIP] Is Office code 688 sent up right?

[Shane Young]

There is no concept of "context" within SIP itself and therefore you  
wouldn't see it in an ENUM entry.

Context, as we use it in this discussion, is  an Asterisk specific  
thing and is why you can include it in the "Inter-Asterisk eXchange  
version 2 protocol (IAX2)" ENUM entry.

In Asterisk configuration, you specify on the inbound peer what  
context to use.  IAX2 gives you the ability to specify multiple  
contexts for that peer and alllow the peer to chose which context they  
want.  The originating asterisk system can specify what context they  
want to use in the call setup.

I don't know if that helps explain it or not.

--Shane



Quoting Greg Blakely <greg at vyger.net>:

> John,
>
> I am not an expert on SIP entries in ENUM.  So, at this time, let me ask
> the group for help on this matter. One of the things I'm unclear about
> is how to include a context entry in SIP connections.  Hopefully,
> someone has a leg up on this, and can get me headed down the right road.
>
> First, though, \\1 translates roughly to "the digits that were queried,"
> usually the digits that were dialed.  So, when I dial 16887070, the enum
> entry I have for you should have me dialing SIP:16887070 at sxs.jj3601.com.
>
>
> As you can see, it includes NO incoming context.
>
> Looking at how I dial out through iConnectHere, a SIP provider, I just
> send the connection request to number at theirserver.  I authenticate by
> registering with them -- which is completely separate from an ENUM
> lookup or dialing string.
>
> I have **got** to be wrong about this!  At least, I hope I am.
>
> Anyone??????
>
>
>> -----Original Message-----
>> From: voip-bounces at ckts.info [mailto:voip-bounces at ckts.info]
>> On Behalf Of john jones
>> Sent: Sunday, October 28, 2007 6:57 PM
>> To: Voice Over IP Tandem for Analog Switches
>> Subject: [VoIP] Is Office code 688 sent up right?
>>
>> Greg,
>>
>> These look very different but maybe they are supposed to?  It
>> looks like maybe the incoming context for 688 is \\1 ???
>>
>>
>> Thanks!
>>
>> John
>>
>> root at Demo_OpenWRT_688:~# dig 1.8.8.6.1.std.ckts.info  NAPTR
>>
>> ;; ANSWER SECTION:
>> 1.8.8.6.1.std.ckts.info. 60     IN      NAPTR   100 10 "u" "E2U+SIP"
>>  "!^\\+*([^\\*]*)!sip:\\1 at sxs.jj3601.com!" .
>>
>> root at Demo_OpenWRT_688:~# dig 1.7.8.6.1.std.ckts.info  NAPTR
>>
>> ;; ANSWER SECTION:
>> 1.7.8.6.1.std.ckts.info. 60     IN      NAPTR   100 10 "u" "E2U+IAX2"
>>  "!^\\+*(.*)$!iax2:inbound at linksys.jj3601.com/\\1!"
>>
>> _______________________________________________
>> VoIP mailing list
>> VoIP at ckts.info
>> http://lists.ckts.info/mailman/listinfo/voip
>> Project Web Page: http://www.ckts.info/
>>
>>
> _______________________________________________
> VoIP mailing list
> VoIP at ckts.info
> http://lists.ckts.info/mailman/listinfo/voip
> Project Web Page: http://www.ckts.info/
>

--Shane
+1-821-7311 CNET

----------------------------------------------------------------