Chappo Posted April 19, 2013 Report Share Posted April 19, 2013 Guys, As the title states I am having some issues with how the internal phones register the incoming calls. The phones on an attended transfer or even picking up an external trunk directly will register either the star code or the person who performed the attended transfer. Is there a way to override this on the pbx side of things? callrecord_received_local0!: email@example.com callrecord_received_local1!: firstname.lastname@example.org callrecord_received_local2!: email@example.com callrecord_received_local3!: firstname.lastname@example.org callrecord_received_local4!: email@example.com callrecord_received_remote0!: sip:firstname.lastname@example.org callrecord_received_remote1!: sip:email@example.com callrecord_received_remote2!: sip:firstname.lastname@example.org callrecord_received_remote3!: sip:email@example.com callrecord_received_remote4!: sip:*firstname.lastname@example.org Trunk Settings: Request-URI Let the System Decide From: Based on trunk account info To: Same as request-URI P-Asserted-Identity: Don't use Header P-Preferred-Identity: Don't use Header Remote-Party-ID: Don't use Header Privacy Indication: Other: id The problem I have is modifying any of these values results in a 502 Bad Gateway error as shown below:  2013/04/19 12:04:41: SIP Rx udp:126.96.36.199:5060: SIP/2.0 502 Bad Gateway Via: SIP/2.0/UDP 172.28.1.5:5060;branch=z9hG4bK-a6f55ac37452f8b6bbc0f28e35179a25;rport To: <sip:email@example.com> From: "JR"<sip:OurPhoneNo@pbx.domain.com.au;user=phone>;tag=13990 Call-ID: 08b383d5@pbx CSeq: 5001 INVITE User-Agent: ENSR188.8.131.52-IS1 Content-Length: 0  2013/04/19 12:04:41: SIP Tx udp:184.108.40.206:5060: ACK sip:firstname.lastname@example.org;user=phone SIP/2.0 Via: SIP/2.0/UDP 172.28.1.5:5060;branch=z9hG4bK-a6f55ac37452f8b6bbc0f28e35179a25;rport From: "JR" <sip:OurPhoneNo@pbx.domain.com.au;user=phone>;tag=13990 To: <sip:email@example.com> Call-ID: 08b383d5@pbx CSeq: 5001 ACK Max-Forwards: 70 Contact: <sip:firstname.lastname@example.org:5060;transport=udp> Privacy: id Content-Length: 0  2013/04/19 12:04:41: INVITE Response 502 Bad Gateway: Terminate 08b383d5@pbx  2013/04/19 12:04:41: SIP Tx tls:172.28.1.84:3629: SIP/2.0 502 Bad Gateway Via: SIP/2.0/TLS 172.28.1.84:3629;branch=z9hG4bK-66fvzg68v8or;rport=3629 From: "JR" <sip:email@example.com>;tag=9q3f1xp4xm To: <sip:firstname.lastname@example.org;user=phone>;tag=a7fad5b5fd Call-ID: 49c270511180-6ninip39wyuz CSeq: 1 INVITE Contact: <sip:email@example.com:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snomONE/5.0.8 Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.