|Summary:||ASTERISK-00157: ENUM Lookups and 482 loopbacks|
|Reporter:||Brian West (bkw918)||Labels:|
|Date Opened:||2003-08-23 20:12:36||Date Closed:||2009-10-05 11:58:16|
|Description:||If sip target is on the same box as the origin endpoint you get a sip 482 loopback. Not sure this is a bug but it would be nice if * would be graceful and understand its own IP in situations like this.|
****** ADDITIONAL INFORMATION ******
-- Executing EnumLookup("SIP/phone1-81ed", "19184290404") in new stack
DEBUG: File enum.c, Line 414 (ast_get_enum): Found technology 'sip', destination 'sip:email@example.com'
ENUM got '1'
-- Executing Dial("SIP/phone1-81ed", "SIPfirstname.lastname@example.org") in new stack
DEBUG: File chan_sip.c, Line 4938 (sipsock_read): Failed to grab lock, trying again...
-- Called email@example.com
DEBUG: File chan_sip.c, Line 515 (__sip_ack): Acked pending invite 102
DEBUG: File chan_sip.c, Line 533 (__sip_ack): Stopping retransmission on 'firstname.lastname@example.org' of Request 102: Found
-- Got SIP response 482 "Loop Detected" back from 18.104.22.168
|Comments:||By: Brian West (bkw918) 2003-08-23 20:13:45|
One last thought would be to use BIND views to hand out diffrent infomation in situations like this. But thats not pratical in some cases.
By: Mark Spencer (markster) 2003-08-24 10:06:51
To break that down would require a level of integration between SIP and ENUM that doesn't exist. For now I'm going to say this isn't fixable.